Release: ASC.ADD 2.6 Last Updated: 10/15/96 Copyright (c) 1995-1996 Advanced System Products, Inc. The AdvanSys OS/2 Universal Driver supports all the AdvanSys SCSI Adapters listed below for the OS/2 2.1 and OS/2 WARP V 3.0, and OS/2 WARP V 4.0 Releases. The OS2 directory includes the following files. The latest versions of these files are maintained on the AdvanSys FTP and BBS sites. If the date listed in this file is more than a few months old, please check the FTP or BBS site for a newer version of the driver. OS2.TXT Installation Instructions ASC.ADD AdvanSys Universal SCSI Adapter Device Driver PRASC.EXE Presence Check Program (Only needed for desktop install) PRASC.DDP Presence Check Definition File (Only needed for desktop install) Supported Adapters ================== The CDB counts below indicate the number of SCSI CDB (Command Descriptor Block) requests that can be stored in the RISC chip cache and board LRAM. A CDB is a single SCSI command. This value can be lowered in the BIOS by changing the 'Host Queue Size' adapter setting. Connectivity Products: ABP510/5150 - Bus-Master ISA (240 CDB) (Footnote 1) ABP5140 - Bus-Master ISA PnP (16 CDB) (Footnote 1) ABP5142 - Bus-Master ISA PnP with floppy (16 CDB) ABP920 - Bus-Master PCI (16 CDB) ABP930 - Bus-Master PCI (16 CDB) ABP960 - Bus-Master PCI MAC/PC (16 CDB) (Footnote 2) Single Channel Products: ABP542 - Bus-Master ISA with floppy (240 CDB) ABP742 - Bus-Master EISA (240 CDB) ABP842 - Bus-Master VL (240 CDB) ABP940 - Bus-Master PCI (240 CDB) ABP940U - Bus-Master PCI Ultra (240 CDB) ABP970 - Bus-Master PCI MAC/PC (240 CDB) Dual Channel Products: ABP752 - Dual Channel Bus-Master EISA (240 CDB Per Channel) ABP852 - Dual Channel Bus-Master VL (240 CDB Per Channel) ABP950 - Dual Channel Bus-Master PCI (240 CDB Per Channel) Footnotes: 1. These boards have been shipped by HP with the 4020i CD-R drive. They have no BIOS so they cannot control a boot device, but they can control secondary devices. 2. This board has been shipped by Iomega with the Jaz Jet drive. Directions are included below for installing the AdvanSys driver with OS/2 WARP V 3.0 (A) and OS/2 WARP V 4.0 (B) to a new system, or to an existing system (C), WARP V 3.0 or V 4.0. A. AdvanSys ASC.ADD Device Driver Installation for OS/2 Warp V 3.0 =================================================================== 1. Obtain the OS/2 WARP V 3.0 CD-ROM installation kit with the following items: a. IBM OS/2 WARP V 3.0 "Installation Diskette for CD-ROM" b. IBM OS/2 WARP V 3.0 "Diskette for CD-ROM (1)" c. IBM OS/2 WARP V 3.0 CD-ROM 2. Make a back-up copy of the diskette "Diskette for CD-ROM (1)". This diskette must be modified to install the ASC driver. 3. The file ASC.ADD must be added to the diskette "Diskette for CD-ROM (1)". Make space on the diskette by removing at least two of the following driver files. Don't remove any drivers that you have Adapter Cards for in your system. These are all drivers for other SCSI Adapter Cards. DPT20XX.ADD, BTSCSI.ADD, AHA152X.ADD, AHA154X.ADD, AHA164X.ADD, AHA174X.ADD, AIC7770.ADD, AIC7870.ADD 4. Use a text editor to add the line "BASEDEV=ASC.ADD" as the last line of the file CONFIG.SYS on the "Diskette for CD-ROM (1)". Remove or comment out with REM the BASEDEV lines in CONFIG.SYS for the driver files that you removed from the diskette. 5. Insert the "Installation Diskette for CD-ROM" into drive A:, insert the install CD-ROM into the CD-ROM drive, and install OS/2 by following the IBM OS/2 installation instructions. 6. After the OS/2 Installation has completed, install the driver from the OS/2 Desktop by following the "Directions for installing the driver to an existing system", Step A. Alternatively you can install the driver manually following Step B. B. AdvanSys ASC.ADD Device Driver Installation for OS/2 WARP V 4.0 =================================================================== 1. Obtain the OS/2 WARP V 4.0 CD-ROM installation CD. Use the CDINST program on the CD to create 3 installation diskettes. After creating the diskettes, you should have the following items. a. IBM OS/2 WARP V 4.0 "Installation Diskette for CD-ROM" b. IBM OS/2 WARP V 4.0 "OS/2 Disk 1" c. IBM OS/2 WARP V 4.0 "OS/2 Disk 2" d. IBM OS/2 WARP V 4.0 CD-ROM 2. Make a back-up copy of the diskette "OS/2 Disk 1" This diskette must be modified to install the ASC driver. 3. Remove Readme.ins file from the diskette "OS/2 Disk 1" to make room. 4. Added ASC.ADD onto the diskette "OS/2 Disk 1". 5. Use a text editor to add two lines "Set CopyFromFloppy = 1" "BASEDEV=ASC.ADD" at the top of the file Config.sys on the "OS/2 Disk 1". 6. Insert the "Installation Diskette for CD-ROM" into drive A, insert the install CD-ROM into the CD-ROM drive, and install OS/2 by following the IBM OS/2 installation instructions. C. Directions for installing the driver to an existing system: ============================================================== Follow (A) for installing from the OS/2 Desktop or (B) for installing from the OS/2 Command Line Desktop. It is recommended that (A) be used because it is simpler to perform. Use either method of installation, but don't use both. A. From the OS/2 desktop: 1. Boot up the existing OS/2 system. 2. Insert the AdvanSys driver diskette in drive A. 3. Select "System Setup" in the "OS/2 System" icon. Select "Device Driver Install" and follow the directions to install the driver. Specify the OS2 directory on the diskette as the "Source Directory". 4. If you would like to add options to the ASC.ADD command line in the CONFIG.SYS file, use a text editor (tedit) from an OS/2 Window command line to edit the CONFIG.SYS file. Find the BASEDEV=ASC.ADD line in the file and add the desired options. Refer to driver options below. 5. Reboot the system by selecting "Shutdown" from the "Launch Pad" icon. B. From the OS/2 command line: 1. Boot up the existing OS/2 system. 2. Insert the AdvanSys driver diskette in drive A. 3. Copy the file ASC.ADD from the diskette OS2 directory to the directory C:\. This assumes that C: is the root drive. Substitute the correct drive letter if your root drive is different. 4. Use a text editor to add the line "BASEDEV=ASC.ADD" as the last line of the drive C: or root drive CONFIG.SYS file. Add any desired options to the line at this time. Refer to driver options below. 5. Reboot the system. AdvanSys Universal SCSI Adapter Device Driver Options ===================================================== /V Verbose Display information during OS/2 system initialization. /A:d Adapter Index "d" is a decimal number. This option is used to specify an adapter for options that follow like /I, /DM, or /SM. The first AdvanSys adapter in the system is numbered 0, the second 1, etc. /C Claim Interrupts The driver will claim ownership of all interrupts it is presented. This option is disabled by default. Refer to the "Troubleshooting and Recovery Suggestions" section below for more information on this option. /I Ignore Adapter Must be preceded by a /A:d option. /[!]DM:target or /[!]DM:(target,lun),... DASD Manager Support: Indicate the unit(s) are to be controlled by OS2DASD.DMD. "target" and "lun" are decimal numbers that specify the devices to use. Must be preceded by a /A:d option. If the '/' is followed by a '!' the unit will not be controlled by OS2DASD.DMD. /[!]SM:target or /[!]SM:(target,lun),... SCSI Manager Support: Indicate the unit(s) are to be controlled by OS2SCSI.DMD. "target" and "lun" are decimal numbers that specify the devices to use. Must be preceded by a /A:d option. If the '/' is followed by a '!' the unit will not be controlled by OS2SCSI.DMD. /L Enable scanning for LUN devices for all targets. By default no LUN scanning is done. /I:port Specify an I/O port address where an AdvanSys ISA or VL adapter card can be found. Up to four of these options can be present on the driver command-line. "port" is a hexadecimal number. /I- Avoid searching for any ISA or VL adapters. /[!]TO Enable/disable software timeouts of disk I/O operations. By default the driver will timeout a disk I/O after 10 seconds. ASC Driver CONFIG.SYS Examples ============================== DEVICE=ASC.ADD /V /I:110 Print adapter and device information during start-up. And only look for ISA or VL type cards at I/O port 0x110. The /I:XXX option does not prevent the driver from finding and controlling EISA and PCI cards. DEVICE=ASC.ADD /I- /L Do not look for any ISA and VL type cards. The driver will only look for and control EISA and PCI cards. For each adapter found scan each target device for LUN devices. BASEDEV=ASC.ADD /A:0 /!SM:5 /!DM:5 Prevent the AdvanSys Adapter 0, Target 5 device from being controlled by the OS2SCSI.DMD and OS2DASD.DMD Device Manager Drivers. If OS2ASPI.DMD is loaded in your CONFIG.SYS it will take control of the device. Troubleshooting and Recovery Suggestions ======================================== Troubleshooting Tip 1: If OS/2 hangs while booting it is possible to see which driver OS/2 is loading when the hang occured. To see drivers listed as they are being loaded do the following: Reboot the system; After the boot manager menu has been exited (if the boot manager is installed) and while the string "OS2" is displayed to the right of a white box in the upper, left-hand corner, press ALT-F2. Each driver that OS/2 loads will be displayed in the lower, left-hand corner of the screen. Troubleshooting Tip 2: To get to an OS/2 prompt of a system that hangs during start-up press ALT-F1 while the string "OS2" is displayed in the upper, left-hand corner. The OS/2 logo will be displayed and then after a few seconds a menu of options will be presented. Choose the option to enter the command line. This will allow you to make changes to your CONFIG.SYS file or install new driver files. The OS/2 editor "tedit" can be used to edit the CONFIG.SYS file. If the above procedure fails boot the "Installation Diskette for CD-ROM" and when prompted insert the "Diskette for CD-ROM (1)". Before the install procedure begins you will be given the option of exiting to the command line by pressing F3. Press F3 to enter the OS/2 command line. Problem 1: OS/2 hangs while loading the ASC.ADD driver and an ASC ISA or VL card is installed and other ISA SCSI cards or network cards are installed. Solution 1: Write down the I/O port address that is printed by the AdvanSys BIOS when the system is booted. Re-boot the system to the OS/2 command line as described above in Troubleshooting Tip 2. Edit the CONFIG.SYS file and add the /I:port address option to the ASC.ADD line to explicitly tell the driver which I/O port the AdvanSys adapter has been configured at. Problem 2: OS/2 panics while loading the ASC.ADD driver with a ASC PCI card installed. OS/2 2.X is being used. The problem does not occur with OS/2 Warp. Solution 2: OS/2 2.X does not support PCI. You must obtain a patch for OS/2 2.X either from IBM or AdvanSys. Contact AdvanSys Customer Support. Problem 3: When installing the ASC driver from the desktop the error message "A profile control file could not be found" is displayed and the installation fails. Solution 3: The "Source Directory" for the install must be set to the directory which contains the files PRASC.DDP, PRASC.EXE, and ASC.ADD. Change the "Source Directory" to this directory. The directory as on the AdvanSys Driver diskette is A:\OS2. Problem 4: Where is the AdvanSys ASPI driver? Solution 4: The ASPI (Advanced SCSI Programming Interface) Driver for OS/2 is provided by IBM. The OS/2 ASPI driver (OS2ASPI.DMD) works with any ADD (Adapter Device Driver) including ASC.ADD. Add the line listed below to your CONFIG.SYS file. Also refer to the Problem below. You may need to add options to your ASC.ADD BASEDEV line to ensure that OS2ASPI.DMD controls a particular device. BASEDEV=OS2ASPI.DMD Problem 5: OS2ASPI.DMD does not report a SCSI device that is installed. Solution 5: Each ADD (Adapter Device Driver) target device can only be controlled/allocated by one DMD (Device Manager Driver). The OS2DASD.DMD (Disk Block Driver), OS2CDROM.DMD (CD-ROM Block Driver), OS2SCSI.DMD (SCSI Pass-Through Driver), and OS2ASPI.DMD (Advanced SCSI Programming Interface Driver) Device Managers control any devices that they find to be unallocated and possibly of a particular type. For example OS2DASD.DMD will only search for and control disk type devices. This "first-come, first-served" device allocation makes the ordering of DMD drivers in the CONFIG.SYS file important. Devices may also be flagged on the ADD line with the /SM and /DM options to prevent them from being controlled by a Device Manager. /SM may be used to prevent OS2SCSI.DMD from controlling a device and /DM may be used to prevent OS2DASD.DMD from controlling a device. OS2CDROM.DMD does not have a similar option. Refer to the section above entitled "AdvanSys Universal SCSI Adapter Device Driver Options" for more information about the /SM and /DM options. The OS2ASPI Device Manager supports two options for device sharing named /ALL and /SHARE. Both of these options prevent OS2ASPI.DMD from exclusively allocating a device which prevents another DMD from using the device. At the same time they allow OS2ASPI.DMD to access a device even if it is controlled by another DMD. The /ALL option prevents the OS2ASPI.DMD from ever attempting to allocate a device. With the /SHARE option OS2ASPI.DMD will only allocate a device while sending a command to the device. Example 1: A CD-ROM drive is attached to AdvanSys Adapter #0 at Target #5 and you want both OS2ASPI.DMD and OS2CDROM.DMD to control the CD-ROM. Use the following lines in the CONFIG.SYS file. BASEDEV=OS2CDROM.DMD BASEDEV=OS2ASPI.DMD /ALL BASEDEV=ASC.ADD /V Example 2: A scanner is attached to AdvanSys Adapter #0 at Target #4 and you are loading both OS2SCSI.DMD and OS2ASPI.DMD, and want OS2ASPI.DMD to exclusively control the scanner. BASEDEV=OS2SCSI.DMD BASEDEV=OS2ASPI.DMD BASEDEV=ASC.ADD /V /A:0 /!SM:4 Problem 6: The ASC.ADD driver does not load at boot time. OS/2 displays a message about there being an error with the driver. After this ASC.ADD displays a message about disabling the BIOS SCAM option. OS/2 may have displayed this message too quickly for it to be readable. Solution 6: If your AdvanSys BIOS does not have the "SCAM Device Support" option then ignore this solution. If your AdvanSys Card BIOS does have the SCAM (SCSI Configured AutoMatic) option make sure that it is disabled. The OS/2 operating system does not have support for this feature. If the ASC.ADD driver detects that the option has been enabled, it will return an error. To correct this problem or check the setting, enter the AdvanSys BIOS by typing Ctl-A during the AdvanSys BIOS Device Scan at boot time. Select the "SCSI Configuration" option and then the "SCAM Device Support" option. If the "SCAM Device Support" option is enabled then disable it, save the change, and reboot the system. Problem 7: The system already had an IDE boot disk and was working fine. An ASC adapter and driver were installed and now the system doesn't boot. The OS/2 logo is displayed and then OS/2 prints a message about not being able to control or find the primary drive. Solution 7: The IBM1S506.ADD (IDE) driver should precede the ASC.ADD driver in the CONFIG.SYS file if the system boots from an IDE drive. OS/2 will boot initially from the BIOS (0x80) boot drive. It will then read the CONFIG.SYS file contained on this boot drive. OS/2 continues its boot procedure with the first ADD BASEDEV driver it finds that controls a fixed disk. If this fixed disk is not the same as the BIOS (0x80) boot disk, OS/2 will actually switch to this different drive to complete booting the system. For this reason the order of BASEDEV ADD lines in the CONFIG.SYS file is very important. If you boot from an IDE drive simply ensure that IBM1S506.ADD is the first BASEDEV line in the CONFIG.SYS file. Problem 8: The system boots very slowly. After the ASC.ADD driver is loaded the AdvanSys adapter or boot disk drive light comes on about once per second. Solution 8: This problem is probably the result of the ASC.ADD interrupt handler not being called by OS/2 after the AdvanSys adapter has completed an I/O. Instead I/O requests are being completed by the ASC.ADD timer interrupt handler which is called once per second. Try setting your AdvanSys adapter IRQ to a different setting using the AdvanSys BIOS. If you have a PCI motherboard and AdvanSys PCI Adapter, try setting the IRQ for the AdvanSys PCI Adapter slot to a different IRQ using the motherboard BIOS. Also if given the option select level-edge triggering for the interrupt. Finally try using the /C driver option, which will cause the ASC.ADD driver to claim all interrupts that it is presented. This option may be needed for systems that happen to generate spurious interrupts on the AdvanSys IRQ. With EISA and PCI bus cards which may share an IRQ with other adapters, each driver indicates whether it claims an interrupt it is presented by setting a different return status. Therefore using the /C option may cause errors in interrupt sharing configurations. Problem 9: The system does not recognize a MO (Magneto-Optical) drive. Solution 9: Add the /V option to the ASC.ADD command line in the CONFIG.SYS file. This will cause the driver to print a banner and information about each device that it detects on the SCSI bus. Check to see if the MO drive is displayed and what device type it is listed with. OS2DASD.DMD will only recognize MO drives when they are set to be "Disk" type devices (SCSI Device Type 0). If the drive is listed as an "Optical Memory" device (SCSI Device Type 7), change the device's setting to "Disk". This can usually be changed with a jumper or switch on the MO drive. When OS2DASD.DMD recognizes the MO drive a removable drive icon will appear in the "Drives" folder. Problem 10: A MO (Magneto-Optical) disk formatted under DOS or Windows is not recognized by OS/2. Solution 10: OS/2 has its own format for MO disks. They are treated like large floppy disks and do not have a partition table. Windows 95 can read OS/2 formatted MO disks, but OS/2 will not recognize MO disks formatted under Windows 95. If you want to transfer MO disks between OS/2 and Windows 95 format the disks under OS/2. Problem 11: An OS/2 installation does not work to an MO (Magneto-Optical) disk. Solution 11: OS/2 has its own format for MO disks. They are treated like large floppy disks and do not have a partition table, because of this OS/2 can not be installed to an MO disk. Problem 12: What are PRASC.DDP and PRASC.EXE and what are they used for? Solution 12: PRASC.DDP is an OS/2 Device Driver Profile file and PRASC.EXE is an OS/2 executable. These are "Presence Check" files that are used with an OS/2 desktop install of the AdvanSys OS/2 Driver. PRASC.EXE exits with a value of 0 if an AdvanSys SCSI Host Adapter is installed in the system and -1 if it encounters an error or if no AdvanSys SCSI Host Adapter is not installed in the system. Once the ASC.ADD driver is installed these two files are not needed. In fact these files are not even needed to install the ASC.ADD driver to the OS/2 CONFIG.SYS file. The ASC.ADD driver can be added to the CONFIG.SYS file with a text editor. Please refer to the section above on installing the ASC.ADD driver from the OS/2 command line. AdvanSys Contact Information ============================ Mail: Advanced System Products, Inc. 1150 Ringwood Court San Jose, CA 95131 Operator: 1-408-383-9400 FAX: 1-408-383-9612 Tech Support: 1-800-525-7440/1-408-467-2930 BBS: 1-408-383-9540 (14400,N,8,1) Interactive FAX: 1-408-383-9753 Customer Direct Sales: 1-800-883-1099/1-408-383-5777 Tech Support E-Mail: support@advansys.com FTP Site: ftp.advansys.com (login: anonymous) Web Site: http://www.advansys.com